home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
gt_power
/
escrub03.zip
/
EMERGE.DOC
< prev
next >
Wrap
Text File
|
1989-12-01
|
5KB
|
121 lines
EMERGE
------
The purpose of the EMERGE program is to combine two files, in the echolist
format, into 1 echolist. The output echolist is composed of all entries
found in either input file. Duplicate entries are reconciled (found in
both input files), so that only 1 entry is placed into the output file.
Here is the command line format:
EMERGE new_echolist old_echolist output
Where:
new_echolist ..... The name of the new echolist file you have received
that you wish to combine with the old echolist. This
could be the output of a prior run of EMERGE, if more
than 1 merge operation needs to be done.
This file could also come from the IEC or other
other echolist source, or it can be obtained from
the ESCRUB program, described in ESCRUB.DOC.
However, it should be noted that the echolist
provided by the IEC is NOT directly importable
by EMERGE, as it most likely does not conform to
the new format. Therefore, manual alteration of
that echolist may be required. The echolist format
used by EMERGE and ESCRUB is compatible with the log
format produced by the ECOxxx.COM program, in use
by local echo coordinators.
old_echolist ..... The name of your old echolist file.
output ........... The result of the reconciliation of the 'new_echolist'
and the 'old_echolist'. After a manual examination this
file can be further processed or used as your working
echolist.
Please note that all input files must be sorted prior to input to this
program. Otherwise, the merge will not match them up correctly. Here is
a sample batch file to run MERGE:
sort <echolist.bbs >eco1
sort <c:\gt\echolist.bbs >eco2
emerge eco1 eco2 out
del eco1
del eco2
Where:
sort ............. The DOS filter. The program is supplied with DOS
version 3.0+. It is used here to insure that the
input files are in conference number order.
echolist.bbs ..... The output of a prior run of EMERGE or ESCRUB. Or,
with modification, an echolist provided by the IEC.
eco1 ............. Temporary work files. They are deleted when no longer
eco2 required.
out .............. The final output file. May be installed as your
working echolist or chained into further runs of
EMERGE, when more than 1 source of echolist is to be
processed.
Echolist Format
---------------
The following is a sample echolist:
E00/001 GT POWER Support 009/000 01:00-06:00
E01/007 The ECHOLIST 009/000 01:00-06:00
E01/008 The NODELIST 009/000 01:00-06:00
Column Contents
------ --------
1-3 Echo Series. Ranges from E00-E99.
Please note that with the advent of G bags and this
new way of maintaining echolists, only E99 conferences
will be considered 'local'. This should be quite
adequate for any net, 1,000 local conferences.
4 '/'. Constant.
5-7 Conference number. Ranges from 000-999.
8 Restriction code:
'p' .... Private conference. Usually by
invitation only.
'a' .... Adult material. Do not expose to minors.
'g' .... GT Sysops only. Others not welcome.
' ' .... Blank - no restriction.
9 Normally blank. Will be set by EMERGE to '·' as a
change marker.
10-55 Conference description.
56 Blank. Constant.
57-59 Net number of sponsor. Must be in range 000-999.
60 '/'. Constant.
61-63 Node number of sponsor. Must be in range 000-999.
64 Blank. Constant.
65-75 The time when the conference is available on the
sponsors system. The format is unrestricted, but is
usually a range of hours in the Central Standard Time
Zone of the U.S.A.
76-? Data following the time is not significant. So comments
might be added.
All files processed by ESCRUB and EMERGE must adhere to this format. Otherwise
the echolist will be malformed.